Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/comment-!build-commands.yml, line 85:

<comment>The `!build-debug` command will never work. The job-level `if` condition (line 24) still gates on `!build-dev`, so a `!build-debug` comment won't even start the job. The job-level condition, the usage comment (line 3), and the error message (line 92) all need to be updated from `!build-dev` to `!build-debug` to match this rename.</comment>

<file context>
@@ -82,10 +82,10 @@ jobs:
         run: |
-          if [[ "${{ github.event.comment.body }}" == "!build-dev" ]]; then
-            echo "command=build-dev" >> $GITHUB_OUTPUT
+          if [[ "${{ github.event.comment.body }}" == "!build-debug" ]]; then
+            echo "command=build debug" >> $GITHUB_OUTPUT
           elif [[ "${{ github.event.comment.body }}" == "!build-profiling" ]]; then
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At tools/building/src/lib.rs, line 74:

<comment>The `ExitStatus` returned by `.wait()` is silently discarded. If the spawned command exits with a non-zero status (i.e., fails), execution continues to the next command without any error. For a build tool where commands are chained sequentially, this means a failed step won't stop the pipeline. Check the exit status and panic (or return an error) on failure.</comment>

<file context>
@@ -0,0 +1,78 @@
+		.unwrap_or_else(|e| {
+			panic!("Failed to run command '{}': {e}", comand.join(" "));
+		})
+		.wait()
+		.unwrap_or_else(|e| {
+			panic!("Failed to wait for command '{}': {e}", comand.join(" "));
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At .nix/default.nix, line 47:

<comment>The `// inputs` merge gives flake inputs precedence over explicitly constructed args. If a flake input name ever collides with a key like `lib`, `pkgs`, or `system`, the carefully constructed value will be silently overridden. Reverse the merge order so explicit values take precedence:
```nix
args = inputs // {
    inherit system;
    ...
};
```</comment>

<file context>
@@ -0,0 +1,81 @@
+          inherit info;
+          inherit deps;
+        }
+        // inputs;
+      in
+      args
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At desktop/bundle/src/common.rs, line 50:

<comment>Return an error instead of panicking so callers can handle command failures via the Result the function already exposes.</comment>

<file context>
@@ -45,7 +47,7 @@ pub(crate) fn build_bin(package: &str, bin: Option<&str>) -> Result<PathBuf, Box
 	let status = Command::new(program).args(args).stdout(Stdio::inherit()).stderr(Stdio::inherit()).status()?;
 	if !status.success() {
-		std::process::exit(1);
+		panic!("Command '{}' with args {:?} failed with status: {}", program, args, status);
 	}
 	Ok(())
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At tools/building/src/deps.rs, line 158:

<comment>Bug: terminal check is on `stdout`, but the prompt is written to `stderr` and input is read from `stdin`. If `stdout` is redirected but `stdin`/`stderr` are terminals, this incorrectly skips the interactive prompt. The check should be on `std::io::stdin()` to determine if a user can respond interactively.</comment>

<file context>
@@ -0,0 +1,185 @@
+		eprintln!("See: https://graphite.art/volunteer/guide/project-setup/");
+	}
+
+	if !installable.is_empty() && std::io::stdout().is_terminal() {
+		eprintln!();
+		eprintln!("The following can be installed automatically:");
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At tools/third-party-licenses/src/main.rs, line 63:

<comment>Prefer returning `ExitCode` from `main()` instead of calling `std::process::exit(1)`. This avoids bypassing Rust's stack unwinding and is the idiomatic way to signal a non-zero exit code now that the heavy lifting is in `run()`.

(Based on your team's feedback about avoiding `exit()` and preferring returning for cleanup.) </comment>

<file context>
@@ -39,6 +58,13 @@ struct Run<'a> {
 fn main() {
+	if let Err(e) = run() {
+		eprintln!("Error: {e}");
+		std::process::exit(1);
+	}
+}
</file context>